Use CARGO_BIN_EXE instead of hardcoded path for tests #98
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
tests/auth.rs
andtests/filters.rs
contains the following path constant for running the binary in tests.This seems to work with
cargo test
since it builds the binary intarget/debug
directory.But in the
cargo test --release
case, those tests fail since the binary is located intarget/release
This pull request removes the hardcoded path constant and uses the
CARGO_BIN_EXE_<name>
environment variable for finding the correct binary path. (See rust-lang/cargo#7697 for more information)